Add to Database

To access this dialog:

Using the Home ribbon, select Database | Add to Database. Select the Underground tab.

The Survey Export dialog is used to commit loaded underground data objects to the survey database, generating files within the current database structure.

The Add to Database panel is used to commit data to the expected database location in an underground survey database, based on the type of data you are adding. You can add data that is specific to a particular decline, area, level or stope. Data can be added at multiple levels, defining a narrower or broader scope as required.

You can view files that have been added to the active database using the Project Data control bar or the Browse Database tool.

Open pit survey data is added using the Open Pit tab.

First, review the Current Decline, Current Area, Current Level and Current Stope assignment. You will be adding data to the context listed here (or you can choose a more general data Scope - see below), but you can edit any item by clicking the corresponding browse button. This displays the Database Settings screen, open at the Declines tab, allowing you to choose another predefined decline, area, level or stope
Select the name of a Surveyor (as defined in your Survey Database settings), then select the Survey date using the date picker provided. Both Surveyor and Survey Date will be embedded within the data that is committed to the current survey database.
Select the Type of Data you are committing to your database. This will provide a list of all loaded objects of that type in the Data Source list.

Alternatively, you can browse your project (or disk) for a file that you wish to commit to the database, using the browse button (...).
Next, select a Data Source. There are three ways to do this;

Select the name of a loaded object from the dropdown list provided.
Use the Data Source browse button to locate a file on disk that you wish to add to the database with the current context. For wireframe files, select the triangle file of the point/triangle pair.
Use the pick button to interactively select data in the 3D window. You will only be able to pick data of the type selected in the Type of Data dropdown list.

Select the Scope of the data you are adding (see Data Scope within the Survey Database Hierarchy)
If you don't wish to use the default data name (e.g. "DevelopmentDesignSolid_MyDecline_MyArea...", "DevelopmentDesignStrings_MyDecline_MyArea..." and so on, you can enter your own file description into the Reference Name field. This will be used to prefix the generated file name, e.g. "MyName_MyDecline_MyArea".
When you are ready, click Add to Database to generate the relevant files and update your project database to point to them. Existing files can be overwritten if you are permitted to do so.

Underground survey data will be linked to the Survey Date, allowing for time period selection in subsequent reporting panels.

The following data type options are available:

Development Design Solids: wireframe data representing expected underground development. Can be added as [Current Level] or [Current Area] Scope.
Development Design Strings: reference string data representing planned underground development. Can be added as [Current Level] or [Current Area] Scope.

Development design string data should contain expected attributes, expected by the development report generator. If mandatory fields cannot be found, the Attribute Mapping dialog will be displayed, allowing you to map existing attributes to mandatory fields required later on. There are also optional fields that can be mapped, which can also be used in downstream reporting.

Development Scan Points: CMS or similar data points representing actual development shapes. Can be added as [Current Level] or [Current Area] Scope.
Development Scan Solids: manually or automatically reconstructed surface data from a CMS scan or similar, representing actual development shapes. Can be added as [Current Level] or [Current Area] Scope.
Stope Design Solids: closed wireframe data representing designed stope shapes, such as those generated by the Datamine's Mineable Shape Optimizer tool. Can be added as [Current Level] or [Current Stope] Scope.
Stope Scan Points: CMS or similar data points representing actual stope shapes. Can be added as [Current Level] or [Current Stope] Scope.
Stope Scan Points: manually or automatically reconstructed wireframe data from original CMS scan points. Can be added as [Current Level] or [Current Stope] Scope.
Surveyed Solids: wireframe data based on collected survey results. Can be added as [Current Level] or [Current Area] Scope.
Surveyed Strings: string data based on collected survey results. Such data can be used to:
- Determine landmark points when constructing a Memo report.
- Constructing drive solids using the Solid task.
This data can be added as [Current Level] or [Current Area] Scope.

If you add wireframe data to the database, and the wireframe(s) in question have a corresponding georeferenced texture file (.bmpx, .pngx or similar), the texture file will automatically be copied to the database in the same location.

Data Scope

The Add to Database screen is used to configure data scope, when it is added to the database.

By default, when you add to the Survey Database, data represents the state of the mine at a given date, and applies to a particular data context, such as a pit and area for open pit surveys (or decline, area, level and stope for underground operations). You can also create data at a more general level.

For example, you may have a string file containing all excavation boundaries for all areas of a pit. In this scenario, you could add the boundary string file to the [Current Pit] level, meaning it will be selectable in all EOM pit reports for the current pit, regardless of the area designation. Similarly, if your project encompassed multiple pits, and the string data contained all boundaries for all pits, it could be added at the [Global] level.

An underground example could be a set of planned design strings representing developments related to the same decline, and applying to multiple areas. In this case, the [Development Design Strings] would be added to the [Current Area]

If you are adding open pit data for a Pit Actual, Design Compliance or Plan Compliance report, you can add data at one of three levels:

Current Area: data added at this level relates to a specific area and pit and will always be used in a report if it exists, otherwise, data for the same Survey date at the Pit or Global level will be used.
Current Pit: data added at this level is accessible to any EOM pit report, regardless of the Area for which the report is being generated, providing area-specific data (see above) for the same Survey date does not exist.
Global: data added at this level is accessible to any EOM pit report, regardless of pit or area reporting context, providing data does not exist at a lower level.

If you are adding data for an open pit ROM report, you can add data at one of two levels:

Current ROM: the ROM data will be specific to a ROM. When a ROM report is run for the given Survey date, this data will be used in preference to any global data that may exist (for the same Survey date).
Global: data added at this level will be (potentially) available to any ROM report for the same Survey date, providing more specific data isn't available (i.e. hasn't been added at the Current ROM level - see above).